QuickOPC User's Guide and Reference
Modifying Information (OPC UA Alarms & Conditions)
Development Models > Imperative Programming Model > Imperative Programming Model for OPC UA Alarms & Conditions > Modifying Information (OPC UA Alarms & Conditions)

Methods described in this chapter allow your application to modify information in the underlying data source that the OPC server connects to or in the OPC server itself (acknowledging conditions). It is assumed that your application already somehow knows how to identify the data it is interested in. If the location of the data is not known upfront, use methods described Browsing for Information chapter first.

The operations performed by the methods described here are actually implemented inside the OPC server. The OPC specification defines OPC UA methods for that, and as such, you could use e.g. one of the EasyUAClient.CallMethod overloads in order to achieve the same outcome. You would have to, however, look up and specify the Node ID of the desired method, and properly assemble the array of input arguments (with proper types), and so on. The methods described below make it easier, and do the boring part for you. They are all implemented in a specialized client object for OPC UA Alarms and Conditions (EasyUAAlarmsAndConditionsClient Class), which you can derive from the IEasyUAClient, or instantiate standalone.

The easiest way to access the functionality is usually to call the AsAlarmsAndConditionsClient Method on the IEasyUAClient Interface you already have. See Specialized Client Objects for more details. For an example of how to do that, see Examples - OPC UA Alarms&Conditions - Acknowledge an event.

The features discussed here, or some of them, may not be available in all editions of the product. Check the Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.
See Also